System and method for navigating in a display window

ABSTRACT

Navigation between a plurality of property sheets on a display of a mobile electronic device, each of the property sheets having a tab index and a layout defining a plurality of elements. One of the property sheets is a displayed property sheet and one of the elements is a current active element. Navigation includes (i) storing the tab index of the displayed property sheet as a current tab index; (ii) detecting a soft key event; regardless of which of the elements is a current active element, (iii) modifying the current tab index based on a soft key identifier of the soft key event to create an updated tab index; and (iv) displaying another property sheet of the plurality of property sheets on the display, the another property sheet having a tab index equal to the updated tab index.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.12/538,984 filed Aug. 11, 2009, which is a continuation of U.S. patentapplication Ser. No. 11/420,250 filed May 25, 2006, now U.S. Pat. No.7,607,105, all the contents of which are herein incorporated byreference in their entirety.

FIELD OF TECHNOLOGY

The present disclosure relates to applications operating upon mobiledevices and, in particular, navigating in a display window.

BACKGROUND INFORMATION

Navigating between tabbed property sheets in a display window of amobile device can be quite a cumbersome experience. One potential reasonfor this difficulty is that the concept of tabbed property sheets wasoriginally designed for display on a traditional computer monitor andnavigation between property sheets was accomplished using a mouse. Thedifficulty in applying this concept to mobile devices arises largely asa result of the reliance of mobile devices on input means such as astylus or a directional pad.

For mobile devices having a stylus, navigation between tabbed propertysheets in a display window can be accomplished by tapping the tabassociated with the desired property sheet with the stylus. The usermust use both hands to accomplish this task as opposed to workingdirectly with the user interface of the mobile device, which can be donewith one hand.

For mobile devices having a directional pad, navigation between tabbedproperty sheets can be accomplished by moving through all of theelements in the current property sheet with the directional pad untilthe tabs (typically at the bottom of the display) are reached and thenpressing the left or right keys of the directional pad to move to thetab corresponding to the desired sheet. The directional pad is intendedfor use in navigating between elements of a property sheet. At any giventime, one of the elements within the property sheet may be the “active”element, e.g. the current control position or the cursor position, andthe directional pad is used to change the active element to the next orprevious element in the layout of the property sheet. Using thedirectional pad, one of the tabs may become the active element bycycling through all the other elements in the layout until that tab isreached. Once that tab has been “activated” as the active element, thenthe directional pad can be used to navigate between property sheets.

Some mobile device displays are also equipped with small left and rightarrow buttons on the screen for revealing tabs that are not visible inthe current display. Navigation to tabbed sheets that are not visible inthe current display involves the further step of ‘clicking’ these arrowbuttons with the stylus in order to reveal the hidden tabs. This actionwill not change the active element and the user must perform the furtherstep of selecting the tab corresponding to the desired property sheet asdescribed previously.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will now be described, by way of example only, withreference to the attached Figures, wherein:

FIG. 1 is a block diagram of an electronic device;

FIG. 2 diagrammatically shows the electronic device of FIG. 1;

FIG. 3 illustrates a screenshot of a tabbed property sheet window; and

FIG. 4 shows, in flowchart form, a method for navigating between aplurality of tabbed property sheets.

Like reference numerals are used throughout the Figures to denotesimilar elements and features.

DETAILED DESCRIPTION

The present disclosure describes methods, devices and computer programproducts for navigating between a plurality of property sheets on adisplay of a mobile electronic device. A particular property sheet isselected using soft keys. These soft keys may be selected via soft keybuttons or soft key icons.

In one aspect, the present disclosure provides a method for navigatingbetween a plurality of property sheets on a display of a mobileelectronic device. Each of the property sheets has a tab index and alayout defining a plurality of elements. One of the plurality ofproperty sheets is a displayed property sheet and one of the pluralityof elements in the displayed property sheet is a current active element.The method includes the steps of storing the tab index of the displayedproperty sheet as a current tab index; detecting a soft key event; andregardless of which of the plurality of elements is the current activeelement, modifying the current tab index based on a soft key identifierof said soft key event to create an updated tab index; and displayinganother property sheet of the plurality of property sheets on thedisplay, the another property sheet having a tab index equal to theupdated tab index.

In another aspect, the present disclosure provides a mobile electronicdevice. The device includes a display for displaying a displayedproperty sheet of a plurality of property sheets. Each of the propertysheets has a tab index and a layout defining a plurality of elements.One of the plurality of elements is a current active element. The mobileelectronic device further comprises a memory component for storing a tabindex of the displayed property sheet, a user input device forinitiating a soft key event; an operating system for detecting the softkey event; and a navigation module responsive to detection of the softkey event regardless of which of the plurality of elements is thecurrent active element. The navigation module includes components for(i) modifying the current tab index based on a soft key identifier ofsaid soft key event to create an updated tab index; and (ii) instructingthe display to display another property sheet of the plurality ofproperty sheets having a tab index equal to the updated tab index.

In yet another aspect, the present disclosure provides a computerprogram product having a computer-readable medium tangibly embodyingcomputer executable instructions for navigating between a plurality ofproperty sheets on a display of a mobile electronic device. Each of theproperty sheets has a tab index and a layout defining a plurality ofelements. One of the plurality of property sheets is a displayedproperty sheet and one of the plurality of elements in the displayedproperty sheet is a current active element. The instructions includeinstructions for; instructions for storing the tab index of thedisplayed property sheet as a current tab index; instructions fordetecting a soft key event; regardless of which of the plurality ofelements is the current active element, instructions for modifying thecurrent tab index based on a soft key identifier of the soft key eventto create an updated tab index; and instructions for displaying anotherproperty sheet of the plurality of property sheets on the display, theanother property sheet having a tab index equal to the updated tabindex.

Other aspects and features of the present disclosure will be apparent toone of ordinary skill in the art in light of the following detaileddescription and drawings depicting one or more embodiments.

FIG. 1 shows a block diagram of an electronic device 10 to which exampleembodiments described herein may be applied. The electronic device 10may comprise a communications subsystem 12 which communicates with awireless network 14. The particular design of the communicationsubsystem 12 will be dependent upon the communication network in whichthe device is intended to operate.

The electronic device 10 may be a hand-held mobile electronic device 10having at least one of data communication capabilities, voicecommunication capabilities and capabilities for communicating with othercomputer systems on the Internet. In various embodiments, mobileelectronic device 10 may be a data communication device, a multiple-modecommunication device configured for both data and voice communication, amobile telephone, a mobile communication device, a PDA enabled forwireless communications, a 1-way or 2-way pager and any type of mobilewireless communication device. It should be appreciated however that thepresent disclosure is in no way limited to these example types ofdevices and may be implemented in other devices. Example embodiments mayalso be applied to non-wireless enabled devices.

The electronic device 10 includes a microprocessor 16 that controls theoverall operation of the device. The microprocessor 16 interacts withcommunications subsystem 12 and also interacts with further devicesubsystems such as the display 18, flash memory 20, random access memory(RAM) 22, auxiliary input/output (I/O) subsystems 24 (which may includea stylus, for example), serial port 26, a keypad or keyboard 28,directional pad 30, quick key buttons 32, soft key buttons 34, speaker36, microphone 38, a short-range communications subsystem 40, and anyother device subsystems generally designated as 42. Of course, anycombination of the above listed device subsystems may be used.

Some of the subsystems shown in FIG. 1 perform communication-relatedfunctions, whereas other subsystems may provide “resident” or on-devicefunctions. Notably, some subsystems, such as display 18, keypad orkeyboard 28, direction pad 30, quick key buttons 32 and soft key buttons34 for example, may be used for both communication-related functions,such as entering a text message for transmission over a communicationnetwork, and device-resident functions such as a calculator or tasklist.

Operating system software 50 (such as, for example, the operating systemWindows Mobile™ marketed by the Microsoft Corporation) and varioussoftware applications 52 used by the microprocessor 16 are, in oneexample embodiment, stored in a persistent store such as flash memory 20or similar storage element. Software applications 52 may include a widerange of applications, including a text messaging application, a ringtone application, a contacts application, and/or a game application.Those skilled in the art will appreciate that the operating system 50and software applications 52, or parts thereof, may be temporarilyloaded into a volatile store such as RAM 22.

The microprocessor 16, in addition to its operating system functions,enables execution of software applications 52. The software applications52 may include host software applications 54 and client softwareapplications 56 on the device.

Host software applications 54 will typically include a predetermined setof applications which control basic device operations and will normallybe installed on the device 10 during manufacture.

One of the client applications 56 may be, for example, a wireless datacommunication application. The wireless data communication applicationmay, for example, enable the receipt and transmission of electronicmessages. In one embodiment, the wireless data communication applicationmay provide for electronic messaging, i.e. E-mail, that is synchronisedand coordinated with a remote electronic messaging server. Electronicmessaging functions provided by the wireless data communicationapplication may include composing messages, saving messages, anddisplaying messages. Other functions or features may include a contactslist or directory, a calendar application, a task list application, aweb browser, and other modules or applications.

Each of the client applications 56 may be a self-contained stand-aloneentity that may have been designed to operate upon a specific ‘native’device. Each client application 56 is typically created and developed bya separate entity than the remainder of the mobile electronic device 10.The client application 56 may be associated with a native environment ordevice in association with which it was originally developed.Accordingly, the client application 56 may include the functions andfeatures associated with its operation on its native device, butpackaged as a stand-alone software entity designed to run on top of athird-party platform in a third-party device.

Alternatively, the client applications 56 may be a self-containedstand-alone entity that may have been designed to operate on a specifichost device with a specific operating system. Such a client application56 may still have been created and developed by a separate entity thanthe remainder of mobile device 10. Accordingly, such a clientapplication 56 may include functions and features associated with knownoperation of the host device, but packaged as a stand-alone softwareentity.

Of course, further software applications 52 may also be loaded onto thedevice 10 through the wireless network 14, an auxiliary I/O subsystem24, serial port 26, short-range communications subsystem 40 or any othersuitable subsystem 42, and installed by a user in the RAM 22 or anon-volatile store for execution by the microprocessor 16. Suchflexibility in application installation increases the functionality ofthe device and may provide enhanced on-device functions,communication-related functions, or both.

The device 10 also includes a navigation module 60. The navigationmodule 60 facilitates quick navigation amongst tabbed property sheetswithout requiring use of the auxiliary I/O subsystem 24 or thedirectional pad 30. The navigation module 60 is responsive to the softkey buttons 34 to provide one-touch movement between property sheetsirrespective of which element in the display 18 is designated as theactive element as will be described in greater detail below. Althoughthe navigation module 60 is referred to as a “module” it will beappreciated that the functions of the navigation module 60 may beimplemented through a variety of programming constructs, which in someembodiments may include subroutines, application programs, objects, orportions or combinations thereof. The use of the terms “module”,“component”, “object”, or other such elements, to refer to softwareprogram elements should be considered as encompassing all such elementas would be suitable in the circumstances, having regard to theprogramming environment, as will be understood by persons of ordinaryskill in the art. It will also be appreciated that, although thenavigation module 60 is shown separately for ease of illustration inFIG. 1, it may form a part of the operating system 50 and/or one or moreapplication programs 52.

Reference is now made to FIG. 2, which diagrammatically shows a frontview of the device 10 of FIG. 1. As mentioned previously, the mobiledevice 10 may be provided with soft key buttons 34. Soft key buttons 34may include a left soft key button 64 and a right soft key button 66.The soft key buttons 34 are multi-function buttons whose active functionis context-dependent. The function of the key buttons 34 in a givencontext is typically indicated on the display screen 18 in the vicinityof the key buttons 34. The function of the key buttons 34 may bedependent upon the window being displayed on the display screen 18 orthe software application 52 active on the display screen 18.

Reference is now also made to FIG. 3, which illustrates a screenshot ofa tabbed property sheet window 62. The soft key buttons 34 in thisembodiment may be associated with soft key icons 68 on the display 18.Soft key icons 68 may include left soft key icon 70 (associated withleft soft key button 64) and right soft key icon 72 (associated withright soft key button 66). Each icon corresponds to a property sheetnavigation action (i.e. left and right). These icons 70 and 72 may bearranged as a soft key bar, as shown. Of course, in some embodiments themobile device 10 may be provided with soft key icons 68 on the display18 without soft key buttons 34. Where both soft key icons 72 and softkey buttons 34 are provided, the soft key icons 72 are located near thesoft key buttons 34. The soft key buttons 34 may not physicallylabelled.

The operating system 50 may associate the soft key buttons 34 and theircorresponding soft key icons 68 with soft key handles, such that whenthe operating system 50 recognizes activation of one of the soft keybuttons 34 or soft key icons 68, the corresponding soft key handle isreferenced for handling the soft key event. These soft key handles maybe assigned to various actions. In typical usage, one soft key handlemay be assigned to a single action and the other one of the soft keyhandles may be assigned to open a menu of actions. The operating system50 may further provide a facility for changing the command or actionassigned to a given soft key handle. This may allow an applicationdeveloper to customize operation of the soft key buttons 34 to theparticular application 52 running on the device 10.

Various ones of the software applications 52 may involve the display ofproperty sheets. A property sheet is a dialog box defined by theoperating system 50 that can be used to view or modify the attributes orproperties of an object (e.g. an object that stores a particular emailoption). Due to the nature of these property sheets, the commands oractions assigned to the soft keys in other contexts may not suitable,and/or may not make sense in the context of all the property sheets. Forexample, a menu of actions for a first property sheet may not beapplicable to a menu of actions for a second property sheet.Accordingly, the soft keys are typically left unassigned or disabled inthe context of tabbed property sheets. In accordance with the presentdisclosure, the soft key handles reference the navigation module 60 forhandling soft key events in the context of tabbed property sheets.

FIG. 3 illustrates a screenshot showing a plurality of property sheets.A displayed property sheet 76 is displayed and is associated withcurrent tab 78 which, in the example embodiment shown, is labelled“General”. Tabs associated with other property sheets are also shown:tab 80 (labelled “Signature”), tab 82 (labelled “Out-of-office”) and tab84 (labelled “Folders”). Each of these tabs has an associated propertysheet which can be displayed by selecting the appropriate tab using, forexample, the auxiliary input/output (I/O) subsystems 24 (which mayinclude a stylus, for example). Of course, the particular labels andproperty sheets described herein are merely examples and any suitablelabelling scheme may be used.

Each one of the plurality of tabbed property sheets has an associatedtab index. With reference to the screenshot of FIG. 3, the current tab78 labelled “General” might have a tab index of “1”, the tab 80 mighthave a tab index of “2”, the tab 82 might have a tab index of “3” andthe tab 84 might have a tab index of “4”. In this example embodiment,the tab indices increase sequentially from left to right, but couldequally increase sequentially from right to left. Similarly, the tabindices need not be numbers but could be any other suitable indicator.

The tab index of the property sheet which is currently displayed isstored as a current tab index in a storage component, such as one of thememory components described previously (e.g. flash memory 20, RAM 22).The operating system 50 (FIG. 1) recognizes the occurrence of a soft keyevent (via a soft key handle), which is initiated by a user inputdevice, e.g. when the user depresses either the left soft key button 64or the right soft key button 66. Alternatively, the soft key event maybe initiated by user selection of the left soft key icon 70 or rightsoft key icon 72 via, for example, the auxiliary input/output (I/O)subsystems 24 (which may include a stylus, for example). The operatingsystem 50 informs the navigation module 60 of the occurrence of the softkey event.

The navigation module 60 may receive a soft key identifier correspondingto the soft key event from the soft key handle. If a left soft keybutton 64 or a left soft key icon 70 has been selected, the soft keyidentifier might be “left” (or any other suitable identifier). Likewise,if a right soft key button 66 or a right soft key icon 68 has beenselected, the soft key identifier might be “right” (or any othersuitable identifier). Alternatively, the identifier may be implicit inthe identity of the soft key handle that messages the notificationmodule 60 if separate soft key handles are designated for the left andright soft key buttons 64 and 66.

The navigation module 60 then retrieves the current tab index frommemory and modifies it based on the soft key identifier. Morespecifically, if the soft key identifier is “left” and the current tabindex is “3”, the navigation module 60 subtracts “1” from the currenttab index to give a current tab index of “2”. Likewise, if the soft keyidentifier is “right” and the current tab index is “3”, the navigationmodule 60 adds “1” to the current tab index to give a current tab indexof “4”. As mentioned previously, the tab indices could also increasesequentially from right to left. If this were the case, if the soft keyidentifier was “left” and the current tab index is “3”, the navigationmodule 60 will add “1” to the current tab index to give a current tabindex of “4”. Likewise, if the soft key identifier was “right” and thecurrent tab index is “3”, the navigation module 60 will subtract “1”from the current tab index to give a current tab index of “2”. Similarmodification schemes could be applied if the tab indices were notnumbers, but rather some other suitable indicator.

Once the navigation module 60 has modified the current tab index, itinstructs the display 18 to display a property sheet having a tab indexequal to the now updated current tab index.

The navigation module 60 is responsive to soft key events regardless ofwhich of the plurality of elements is the current active element (i.e.regardless of what the user is doing or where the cursor is on thedisplay). An example active element 58 is shown in FIG. 3. Further, whennavigating between property sheets, a default active element may be setfor a given property sheet such that, when the device 10 displays a newproperty sheet, the active element will not necessarily be the tab. Forexample, the default active element may be a text control of theproperty sheet. If the directional pad or a stylus were used to switchto a new property sheet (as described previously), the active elementwould be located at the property sheet tab and the user would have tomove through the elements to get to a desired active element.

While left soft key icon 70 and right soft key icon 72 might display thetext “previous” and “next”, as shown in FIG. 3, it should be understoodthat any suitable text could be used (such as “left” and “right” and soon). Similarly, the text could be replaced by images of arrows or thelike (thus dispensing with the need to translate text for use in otherlanguages).

It should also be understood that the appearance and placement of thesoft key icons 68 and soft key buttons 34 are not limited to theappearance and placement shown in FIG. 3. Further, it should beunderstood that as some mobile devices do not have buttons similar tosoft key buttons 34, or do not always have such buttons accessible (e.g.swivel-type mobile phones), these devices would only utilize soft keyicons 68.

As subsequent property sheets are displayed, the tabs themselves mightalso slide to the left and right as necessary so that at least the tabimmediately to the left and right of the current tab is always visible(so that the user can see where they might potentially move to next).However, if this sliding functionality is not provided, it should beunderstood the soft key icons 68 or buttons 34 could be used to displayproperty sheets associated with tabs which are hidden (i.e. off thescreen).

It should be noted that while each one of the plurality of propertysheets described herein has an associated tab shown, it should beunderstood that such tabs as not necessary. Each sheet may be identifiedby its tab index without actually displaying a physical tab.

It should be noted that while in the above description, the operatingsystem 50 and other features are described as having the characteristicsof Windows Mobile™, it should be understood that embodiments describedherein could also be applied to other operating systems.

Reference is now made to FIG. 4, which shows, in flowchart form, amethod 100 for navigating between a plurality of property sheets on adisplay of a mobile electronic device. As mentioned previously, each oneof these property sheets has a tab index and the tab index of theproperty sheet currently displayed is stored as a current tab index. Themethod begins in step 102 where a soft key event is detected. Next, thesoft key identifier of the soft key event is determined (step 104). Thecurrent tab index is then retrieved (step 106).

In the next step (step 108), a determination is made as to whether thecurrent tab index is a leftmost tab index or a rightmost tab index. Ifthe current tab index is a leftmost tab index and the soft keyidentifier is a left identifier or if the current tab index is arightmost tab index and the soft key identifier is a right identifier,the remaining steps shown in FIG. 4 are skipped and the navigationmodule 60 waits for the next soft key event. Optionally, an errormessage may be displayed to indicate that no further property sheets areavailable in the selected direction. Further, the property sheets may bearranged cyclically so that if user selects the left soft key when thecurrent tab index is the leftmost tab index, the navigation module 60will display the property sheet associated with the rightmost tab index.

Otherwise, the current tab index is modified based on the soft keyidentifier (step 110). Finally, a second property sheet of the pluralityof property sheets is displayed. This second property sheet has a tabindex equal to the current tab index (step 112). Once step 112 iscomplete, the navigation module 60 waits for the next soft key event.

The above-described embodiments of the present disclosure are intendedto be examples only. Alterations, modifications and variations may beeffected to the particular embodiments by those skilled in the artwithout departing from the scope of the disclosure, which is defined bythe claims appended hereto.

The invention claimed is:
 1. A method for a mobile device for navigatingbetween a plurality of property sheets on a display of the mobiledevice, each of the property sheets having a tab index and a layoutdefining a plurality of elements, the method comprising: assigningnavigation functions to two soft keys for navigating between saidplurality of property sheets, the navigation functions being indicatedon a display in the vicinity of the keys; storing the tab index of thedisplayed property sheet as a current tab index; detecting a soft keyevent; and modifying said current tab index based on a soft keyidentifier of said soft key event to create an updated tab index; anddisplaying another property sheet of said plurality of property sheetson said display, said another property sheet having a tab index equal tosaid updated tab index.
 2. A method according to claim 1, furthercomprising determining said soft key identifier and/or retrieving saidcurrent tab index before said modifying of said current tab index basedon said soft key identifier of said soft key event to create saidupdated tab index.
 3. A method according to claim 1, wherein said softkey identifier is one of a left identifier and a right identifier.
 4. Amethod according to claim 3, wherein said modifying comprisesincrementing said current tab index if said soft key identifier is saidright identifier and decrementing said current tab index if said softkey identifier is said left identifier.
 5. A method according to claim4, wherein said modifying comprises: determining if said current tabindex is a leftmost tab index or a rightmost tab index, and performingsaid incrementing or decrementing unless said current tab index is aleftmost tab index and said soft key identifier is a left identifier orunless said current tab index is a rightmost tab index and said soft keyidentifier is a right identifier.
 6. A method according to claim 1,wherein said detecting of a soft key event comprises detectingactivation of one of a left soft key and a right soft key.
 7. A methodaccording to claim 1, wherein said two keys are associated with two softkey icons on the display, each icon corresponding to a property sheetnavigation action.
 8. A method according to claim 1, further comprisingdefining a soft key bar within said display, said soft key barcomprising two soft key icons, said two soft key icons corresponding totwo property sheet navigation actions.
 9. A method according to claim 8,wherein said two property sheet navigation actions comprise left andright.
 10. A method according to claim 1, wherein said modifying isperformed by a navigation module and wherein the method furthercomprises an initial step of associating a soft key handle with saidnavigation module.
 11. A method according to claim 2, wherein saiddetermining is performed by a navigation module and wherein the methodfurther comprises an initial step of associating a soft key handle withsaid navigation module.
 12. A method according to claim 2, wherein saidretrieving is performed by a navigation module and wherein the methodfurther comprises an initial step of associating a soft key handle withsaid navigation module.
 13. A method according to claim 1, wherein saidplurality of elements within said displayed property sheet comprises atab element, and wherein said current active element is one of saidplurality of elements other than said tab element.
 14. A methodaccording to claim 4, wherein said modifying comprises: determining ifsaid current tab index is a leftmost tab index or a rightmost tab index;and if said current tab index is said rightmost tab index and said softkey identifier is said right identifier, performing said incrementing bysetting said current tab index to said leftmost tab index, and if saidcurrent tab index is said leftmost tab index and said soft keyidentifier is said left identifier, performing said decrementing bysetting said current tab index to said rightmost tab index.
 15. A mobilecommunications device, comprising: a display for displaying a propertysheet of a plurality of property sheets, each of the property sheetshaving a tab index and a layout defining a plurality of elements; afirst and a second soft key, for initiating soft key events and operableto be assigned navigation functions for navigating between saidplurality of property sheets, wherein the assigned navigation functionsof the soft keys are indicated on the display in the vicinity of thekeys; a memory component for storing the tab index of a displayedproperty sheet as a current tab index; an operating system for detectingsoft key events initiated by said soft keys; and a navigation moduleresponsive to detection of a soft key event by said operating systemafter said soft keys have been assigned a navigation function to: modifythe current tab index based on a soft key identifier of said soft keyevent to create an updated tab index; and instruct the display todisplay another property sheet said plurality of property sheets, thetab index of said another property sheet being equal to said updated tabindex.
 16. A mobile communications device according to claim 15, whereinsaid soft key identifier is one of a left identifier and a rightidentifier, and wherein said modifying comprises incrementing saidcurrent tab index if said soft key identifier is said right identifierand decrementing said current tab index if said soft key identifier issaid left identifier.
 17. A mobile communications device according toclaim 15, wherein said navigation module is further configured fordetermining said soft key identifier of said soft key event.
 18. Amobile communications device according to claim 15, wherein saidnavigation module is further configured for retrieving said current tabindex from said memory component.
 19. A mobile communications deviceaccording to claim 15, wherein said soft key event is initiated when auser depresses one of said soft keys.
 20. A mobile communications deviceaccording to claim 15, wherein each of said soft keys are associatedwith soft key icons on the display, each icon corresponding to aproperty sheet navigation action.
 21. A mobile communications deviceaccording to claim 16, wherein said navigation module is furtherconfigured for: determining if said current tab index is a leftmost tabindex or a rightmost tab index; and performing and incrementing ordecrementing unless said current tab index is a leftmost tab index andsaid soft key identifier is said left identifier or unless said currenttab index is a rightmost tab index and said soft key identifier is saidright identifier.
 22. A mobile communications device according to claim16, wherein said navigation module is further configured for:determining if said current tab index is a leftmost tab index or arightmost tab index; and if said current tab index is said rightmost tabindex and said soft key identifier is said right identifier, performingsaid incrementing by setting said current tab index to said leftmost tabindex, and if said current tab index is said leftmost tab index and saidsoft key identifier is said left identifier, performing saiddecrementing by setting said current tab index to said rightmost tabindex.
 23. A non-transitory machine-readable medium embodying programcode means executable upon a processor of a mobile communications devicecontaining instructions for assigning navigation functions to two softkeys of the mobile communications device having a display, the assignedfunctions being indicated on the display, and utilising the soft keys tonavigate between a plurality of property sheets on the display, each ofthe property sheets having a tab index and a layout defining a pluralityof elements, wherein one of the plurality of sheets is a displayedproperty sheet, the program code comprising: instructions for assigningnavigation functions to the two soft keys for navigating between saidplurality of property sheets, the navigation functions being indicatedon the display in the vicinity of the keys; instructions for storing thetab index of the displayed property sheet as a current tab index;instructions for detecting a soft key event; instructions for modifyingsaid current tab index based on a soft key identifier of said soft keyevent to create an updated tab index; and instructions for displayinganother property sheet of said plurality of property sheets on saiddisplay, said another property sheet having a tab index equal to saidupdated tab index.
 24. A method according to claim 1, wherein the softkeys each comprises a soft key button.
 25. A mobile communicationsdevice according to claim 15, wherein the soft keys each comprises asoft key button.
 26. A non-transitory machine-readable medium accordingto claim 23, wherein the soft keys each comprises a soft key button.